|
|
|
|
|
|
|
engineering and reverse code engineering to drastically reduce these risks. Because you used Rational Rose/Visual Basic for the use cases on Day 2, you should use Microsoft Visual Modeler in this chapter. Note that the processes of creating code from models and reverse engineering existing code are exactly the same in both products, so you will be able to use the following steps in either tool. If you own Visual Basic Professional or Enterprise, you can go to www.microsoft.com/vbasic, register in the Owners' Area as a licensed user, and download Visual Modeler for free. Otherwise, you need to go to www.rational.com and make arrangements to pay for Rational Rose/Visual Basic. If nothing else, you can still model your classes by hand. |
|
|
|
|
|
|
|
|
Generating Code for the Samsona Bank Teller System Example |
|
|
|
|
|
|
|
|
After verifying the design models with peer architects at your company and with your client, you're ready for construction to begin. To keep things simple, your iteration plan only includes one iteration, meaning that all use cases must be implemented. You had anticipated the need for only one additional programmer, but after reviewing your design models, you make a better staff resource estimate that calls for two additional programmers, which your client agrees to. In reviewing the design models and project plans with your programmers, you advise them to refrain from activities that could lead to scope creep, such as making assumptions about requirements. If additional requirements are discovered, you advise your programmers to review them with you first. |
|
|
|
|
|
|
|
|
For the application's architecture, you list the various components, mechanisms, and design patterns you plan to use. You expect to use any controls that ship with Visual Basic, plus the following subsystems: |
|
|
|
 |
|
|
|
|
Graphical User Interface Subsystem |
|
|
|
|
|
|
|
|
Workgroup and User Security Subsystem |
|
|
|
|
|
|
|
|
Internal Application Manager Subsystem |
|
|
|
|
|
|
|
|
Business Rules Subsystem |
|
|
|
|
|
|
|
|
Reporting and Printing Subsystem |
|
|
|
|
|
|
|
|
File Operations Subsystem |
|
|
|
|
|
|
|
|
Error-Processing and Exception-Handling Subsystem |
|
|
|
|
|
|
|
|
Database Access Subsystem |
|
|
|
|
|
|
|
|
(Each subsystem will be covered in detail in subsequent chapters.) Your programmers are impressed with this separation of concerns and are eager to begin. |
|
|
|
|
|